fix(ci-lease): chained-assume session capped at 1h#397
Merged
Conversation
AWS limits role-chaining (sigv4 from already-assumed creds) to a 1h session regardless of the target role's MaxSessionDuration. The previous 21600s (6h) request returned: Could not assume role with user credentials: The requested DurationSeconds exceeds the 1 hour session limit for roles assumed by role chaining. This is the last documented blocker for the assume step. Smart-car-park PR-run got to "Lease Active. account_id=024863981725" and was already acquiring the role — just couldn't request 6h.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AWS limit: chained assumes are 1h max regardless of MaxSessionDuration. Previous 6h request returned ValidationError.